Models
Epicenter applications are powered by models.
Overriding model context
All functions of the Run adapter that start a run, offer the option of providing a partial context file in the modelContext param. The functions will load the model's context file if one exists and use the partial context you provide to override values in the model's file.
Epicenter worker
The worker is a process that loads your model code as a module. The worker is responsible for encoding your model's variable values in JSON and storing them in or retrieving them from the database.
To specify a worker image, edit the workerImage property in the model context file.
Proxies
In an Epicenter project, a proxy is used to handle permission elevations. A proxy has higher permissions than a user. It can authenticate users and allow them to perform specific actions they are not ordinarily allowed to perform.
A proxy starts an HTTP daemon and Epicenter maps the proxy's HTTP port out to make it available for your simulation UI code.
Use a proxy to implement fine-grained permissions in scenarios that can't be handled using Epicenter permissions and permits.